feat(cli): migrate provider authoring surface - #1714

Summary

AgentV's authored provider surface now uses the Promptfoo-aligned provider vocabulary consistently across the CLI, config discovery, docs, and examples. Users select configured providers with --provider / --providers, authored catalogs resolve from providers.yaml, and target-era authored inputs hard-error with migration guidance instead of silently falling back.

This intentionally does not change generated run-bundle artifact filenames. Bundle output still writes the existing targets.yaml artifact path so av-kfik.51 can own that artifact migration without this branch preserving or copying legacy bundle files.

What Changed

• Provider catalog discovery now prefers providers.yaml / .agentv/providers.yaml and hard-rejects authored targets.yaml files.
• Eval, bundle, pipeline, and prepare command surfaces expose provider flags while old target flags report hard-deprecation diagnostics.
• Init/create/interactive output, current docs, README, and examples now describe authored provider config with providers, label, and id semantics.
• Example provider catalogs were renamed from targets.yaml to providers.yaml where they are authored inputs.

Validation

• bun test apps/cli/test/commands/eval/run-command-options.test.ts apps/cli/test/commands/eval/targets.test.ts apps/cli/test/commands/eval/bundle.test.ts apps/cli/test/commands/prepare/prepare.test.ts apps/cli/test/commands/grade/grade-prepared.test.ts apps/cli/test/eval.integration.test.ts packages/core/test/evaluation/providers/targets-file.test.ts
• bun run validate:examples
• bun --filter agentv typecheck
• bunx @biomejs/biome@1.9.4 check on changed TS/JS/MD/JSON files
• git diff --check

Post-Deploy Monitoring & Validation

No additional operational monitoring required. This is a CLI/docs/config migration with no hosted runtime path; GitHub Actions and downstream CLI smoke usage are the relevant validation surfaces.

Related

Related: av-kfik.52